Magnum One/Magnum One (Mid-American Digital) (Disc Manufacturing).iso/d19/win3pcb2.arc/WIN3PCB.TXT

Text File | 1990-12-25 | 1.8 KB | 40 lines

In posting these files, I'm not claiming this is the way that PCBoard
14.5/E3 should be set up to run two nodes under Windows.  This is merely
the way I am successfully running two nodes (and a maintenance node with
no modem) under Windows day in and day out for quite a while, now.

The way I've set up my system is that each node has its own full set of
executables in its own subdirectory.  Beyond that, most text files, etc.
are "shared" between the nodes. The exceptions aren't really worth
mentioning except to note that the degree to which PCBoard can be
customized is remarkable.

These PIF files call BOARD.BAT, BOARD2.BAT, and BOARD3.BAT. As far as I can
tell, the batch files are the stock model, straight off the showroom floor,
with editing only for the node's subdirectory, etc.

I have a clone Hayes 2400 modem on Node 1 (which to confuse matters is on
com2) and a Hayes V-series 9600 opening at 19200 on Node 2 (and com1). I
plan to eventually put node 1 on com1, but it works fine this way and I
have no interest in messing with success until there's nothing else to do.

There are a few lines in WIN.INI and SYSTEM.INI worth noting -- especially
SYSTEM.INI's DMABUFFERSIZE=50 (32 will do), its SYSTEMROMBREAKPOINT=FALSE,
and its VCPIWARNING=FALSE. These additions were necessitated by 386MAX
v5.1 and may not be needed when running any other extended memory driver.

I am using SMARTDRV.SYS as my disk cache, and it really speeds up disk
intensive tasks like directory searches (for example, Z)ippy dir searches)
or complex message searches (especially when I have several hundred
messages in a conference message base (for example, in the Software
conference, I never kill messages that have to do with software.)

Good luck

Steve Konicki
SysOp, The Cabana BBS
Tallahassee, FL
[phone]